The following sections identify the modifications to the allShare product since the release of allShare v1.1 in July of 1990.
v1.1.1 release notes:
- fixes a problem with Finder copies that prevented the user from copying/duplicating locked files (locked checkbox in Get Info Dialog).
v1.1.2 release notes:
- allShare can now publish A/UX v2.0 volumes on the network
- install instructions for A/UX users are specified below
- fixed problems on allShare installation (during a startup or restart) when the user didn't have AppleTalk active (using the chooser). This resulted in "Unknown Errors" during Finder copies and duplicates.
v1.1.3 release notes:
The following release of allShare represents only fixes to specific problems reported with allShare 1.1.2. The following changes have been made:
1) shutdown dialogs are now stored in the system heap for use instead of depending on the allShare file being available to open under low RAM conditions for shutdown. This makes the shutdown dialog available even when some of the system heap becomes corrupt. Also, this change should solve some problems when shutdown is chosen on an A/UX serving client (since A/UX pulls the rug out).
2) timeouts for writing packets to the server have been extended to compensate for gateways using slower transmission mediums (ie modem/router systems).
3) Works v2.0 and FileMaker Pro both attempt to open a file with exclusive access and then do the same call again to ensure that denyMode operations are available on this server. The second open is suppose to fail and it does but allShare wasn't placing the fileNumber into the reply packet correctly.
4) Local file open calls in some newer programs (among them Works 2.0 and FileMaker Pro) were executing an OpenDeny call locally using working directories ╤ which allShare didn't process correctly and returned as an error. Apple documents OpenDeny calls as HFS only which implies that working directories won't be used. This could result in "could not be opened", "file is locked or busy" or "file not found" errors depending on the program. After receiving one of these errors, the user might not be able to unmount the volume or re-open the file (locally or over the network). Version 1.1.3 now handles these "interpretations" of the OpenDeny call correctly.
5) Volume lock and file lock errors were not being translated to the correct AFP error code so clients of an allShare server may have been getting improper error messages in these cases.
6) Under very unusual cases, allShare permitted two users exclusive Read/Write access to the file. This (obviously) meant that the file wasn't the exclusive and caused record locking conflicts - AT NO TIME HAS THIS CAUSED DATA CORRUPTION. Our byte-range locking code compensated for the exclusive access the first time the second user tried to write to the file ╤ albeit a little late.
